So you're saying that the reason the Emplode media check didn't fix the problem is because his drive was too big?

...and the amount of available memory too small. Yes. Or at least, that is what I suspect. In order to prove it, I would have to find out if the fsck that emplode performs can direct output over the serial port. I have not tried that particular step yet.

But I do know that if I perform a manual fsck on the 80GB drives from command line and the drives are almost full and I forget to turn on swap in advance, I will get an error from stage 5 of the fsck because it could not allocate enough space to complete the step.

Hm... It is a quiet morning. This may take some time, but I will try to get some output of this. It might be a good troubleshooting step, and perhaps good data for 3.0 enhancements. (Note: I am running 2.0final developer.)